Engine health and life cycle tracking system

ABSTRACT

An engine-mounted component life cycle data tracking system is provided. The system includes a plurality of RFID tags associated with, positioned proximate to, and configured to transmit and store identification, repair history, and dynamic data regarding a different engine component of a plurality of engine components, wherein the dynamic data includes engine usage, component usage, and/or component fault information. The system further includes an aircraft-mounted controller that includes non-transient computer readable storage media. The controller is configured to: store identification and repair history data retrieved from the RFID tags in the storage media; store dynamic data for the plurality of engine components in the storage media after each engine cycle; and transmit dynamic data to the RFID tags after each engine cycle for storage. After each engine cycle, the aircraft-mounted controller includes in its storage media the identification, repair history and dynamic data for the plurality of engine component.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit as a continuation of U.S. patentapplication Ser. No. 15/483,563, having the same title as thisapplication, and filed on Apr. 10, 2017. This application incorporatesthe prior application into the present application by reference.

TECHNICAL FIELD

The technology described in this patent document relates generally toaircraft engine component life cycle tracking systems and moreparticularly to using RFID tags to track the life cycle of aircraftengine components.

BACKGROUND

Aircraft engine component maintenance data such as LRU and componentlife in hours, operating cycles, associated engine and overhaulinformation is typically recorded manually. Because data is recordedmanually, errors may occur in the recording of data and the data may notbe recorded in real time. Accordingly, it is desirable to provide anautomated system that can automatically record engine componentmaintenance data.

SUMMARY

This summary is provided to describe select concepts in a simplifiedform that are further described in the Detailed Description. Thissummary is not intended to identify key or essential features of theclaimed subject matter, nor is it intended to be used as an aid indetermining the scope of the claimed subject matter.

A method in an aircraft-mounted controller is provided. The methodincludes reading data from and writing data to a plurality of radiofrequency identification (RFID) tags positioned around an aircraftengine wherein each RFID tag is associated with and positioned proximateto a different one of a plurality of engine components and each RFID tagis configured to transmit and store data regarding its associated enginecomponent. The method further includes storing in a component databasestatic data, repair data, and dynamic data regarding the plurality ofengine components wherein the static data includes identificationinformation regarding the engine components, the repair data includesrepair history information regarding the engine components that isrecorded by the RFID tags during visits by their associated enginecomponent to a repair shop, and the dynamic data includes engine usageinformation, component usage information, and component faultinformation regarding the engine components. The method further includestransmitting the dynamic data regarding the associated engine componentto each RFID tag after each engine cycle for storage in the RFID tag andtransmitting static data, repair data, and dynamic data regarding one ofthe engine components to an external system responsive to a request bythe external system.

An engine-mounted component life cycle data tracking system is provided.The system includes a plurality of radio frequency identification (RFID)tags positioned around an aircraft engine wherein each RFID tag isassociated with and positioned proximate to a different engine componentand each RFID tag configured to transmit and store data regarding itsassociated engine component. The system further includes anengine-mounted communication module configured to read data from andwrite data to each RFID tag and an aircraft-mounted controller incommunication with the engine-mounted communication module. Theaircraft-mounted controller is configured to perform operations toretrieve, using the communication module, static data and repair datafrom each RFID tag wherein the static data includes identificationinformation regarding the engine component and the repair data includesrepair history information regarding the engine components resultingfrom any visit by any of the engine components to any repair shop. Theaircraft-mounted controller is further configured to store the staticdata and the repair data for each engine component in a database in thecontroller and store dynamic data in the database for each enginecomponent after each engine cycle wherein the dynamic data includesengine usage information, component usage information, and componentfault information regarding the engine component. The aircraft-mountedcontroller is further configured to transmit, using the communicationmodule, the dynamic data regarding the engine component to each RFID tagafter each engine cycle for storage in the RFID tag

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingdetailed description when read with the accompanying figures, whereinlike numerals denote like elements, and

FIG. 1 is a block diagram depicting example components on an exampleaircraft engine, in accordance with some embodiments;

FIG. 2 is a process flow chart depicting an example process in anaircraft-mounted controller for tracking engine component life cycledata, in accordance with some embodiments;

FIG. 3 is a process flow chart depicting another example process in anaircraft-mounted controller for tracking engine component life cycledata, in accordance with some embodiments;

FIG. 4 is a process flow chart depicting another example process in anaircraft-mounted controller for tracking engine component life cycledata, in accordance with some embodiments; and

FIG. 5 is a process flow chart depicting another example process in anaircraft-mounted controller for tracking engine component life cycledata, in accordance with some embodiments.

DETAILED DESCRIPTION

The subject matter described herein discloses apparatus, systems,techniques and articles for automatically tracking engine component lifecycle data. The following detailed description is merely exemplary innature and is not intended to limit the invention or the application anduses of the invention. As used herein, the word “exemplary” means“serving as an example, instance, or illustration.” Thus, any embodimentdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other embodiments. All embodimentsdescribed herein are exemplary embodiments provided to enable personsskilled in the art to make or use the invention and not to limit thescope of the invention which is defined by the claims. Furthermore,there is no intention to be bound by any expressed or implied theorypresented in the preceding technical field, background, summary, or thefollowing detailed description.

FIG. 1 is a block diagram depicting example components on an exampleaircraft. The example aircraft includes an engine mounted communicationmodule 102, an aircraft mounted engine electronic controller 104, and aplurality of engine components comprising a plurality of linereplaceable units (LRUs) 106, 108, 110, 114, 122, 124, 126 and otherengine components 112, 116, 118, 120. The LRUs 106, 108, 110, 114, 122,124, 126 and the other engine components 112, 116, 118, 120 are eachequipped with radio frequency identification (RFID) tags mounted on orproximate thereto that can transmit, receive, and store data. The enginemounted communication module 102 can communicate with each of the RFIDtags to retrieve data transmissions from the RFID tags and to transmitdata to the RFID tags for storage.

The engine mounted communication module 102 also communicates with anaircraft mounted engine electronic controller 104 and acts as anintermediary between the electronic controller 104 and the RFID tags.The communication module 102 receives data in the form of RFtransmissions from the RFID tags and relays the data to the electroniccontroller 104. The communication module 102 also receives informationfrom the electronic controller 104 and transmits the information to theRFID tags. In this example, the engine mounted communication module 102can further communicate wirelessly via cellular transmissions, satellitetransmissions, and/or other wireless transmissions to one or moreexternal systems 128 (such as an aircraft maintenance system or enginemaintenance system) to download data to the external system 128. Inother examples, the engine mounted communication module 102 may notcommunicate wirelessly.

The engine mounted communication module 102 therefore may include an RFtransceiver to facilitate information exchange between the RFID tags andthe communication module 102. The engine mounted communication module102 may also include a cellular transceiver, satellite transceiver,and/or other wireless transceiver to facilitate an information exchangebetween an external system 128 and the communication module 102.

The LRUs in the example aircraft 100 include an IGV actuator 106, a fuelmodule 108, a surge control valve 110, a bleed valve 114, a lube module122, starter/generator system 124 and an exciter 126. The other enginecomponents in the example aircraft 100 include fuel nozzles 112, aninlet scroll 116, turbines and compressor wheels 118, and an enginegearbox mounted nameplate 120. Each of the LRUs and other components inthis example includes an associated RFID tag that is mounted on or nearthe engine component.

The RFID tags are configured to receive data for storage, store receiveddata, and to transmit stored data. In this example, each RFID tag storesstatic, repair, and dynamic data regarding the LRU or other enginecomponent with which the RFID tag is associated. The static dataincludes identification information regarding the associated enginecomponent, the repair data including repair history informationregarding the associated engine component that is recorded by the RFIDtag, for example, during visits by the engine component to a repairshop, and the dynamic data includes engine usage information, componentusage information, and component fault information regarding theassociated engine component.

The identification information may be stored in the RFID tag around thetime the RFID tag is mounted on the engine component. As an example, theidentification information for the IGV actuator 106, fuel module 108,surge control valve 110, fuel nozzles 112, bleed valve 114, inlet scroll116, turbine and compressor wheels 118, engine gearbox nameplate 120,lube module 122, starter/generator systems 124, and exciter 126 may eachinclude a part number and a serial number.

The dynamic data may be periodically updated and received from an enginecontroller 104 via the control module 102 and stored when received. Thedynamic data may include engine usage information, component usageinformation, and component fault information regarding the enginecomponent. The engine usage information may include operating hours andoperating cycles experienced by the engine. The component usageinformation may include operating hours and operating cycles experiencedby the engine component. The component fault information may includefault codes and fault messages.

The dynamic data may include environmental measurements such astemperature, vibration, ice accumulation, and others. The dynamic datafor one engine component may be different from the dynamic data foranother engine component. As an example, the dynamic data for the IGVactuator 106, fuel module 108, and fuel nozzles 112 may each includetemperature, vibration, operating hours and operating cycles. Thedynamic data for the surge control valve 110 and the exciter 126 mayeach include total operating hours and operating cycles. The dynamicdata for the bleed valve 114 may include temperature, vibration,operating hours and open/close cycles. The dynamic data for the inletscroll 116 may include ice accumulation, operating hours, and operatingcycles. The dynamic data for the lube module 122 may includetemperature, operating hours, and operating cycles. The dynamic data forthe turbine and compressor wheels 118, engine gearbox nameplate 120, andstarter/generator systems 124 may include operating hours and operatingcycles.

The engine electronic control module 104 may comprise one or moreprocessors and be configured by computer programming instructions toperform its functions. The engine electronic control module 104 may beconfigured to retrieve, using the communication module, static data andrepair data from each RFID tag, store the static data and the repairdata for each engine component in a database in storage media accessibleby the controller, and store dynamic data in the database for eachengine component, for example, after each engine cycle. The engineelectronic control module 104 may also be configured to transmit, usingthe communication module, dynamic data regarding an engine component toeach engine component's associated RFID tag, for example, after eachengine cycle for storage in the RFID tag. The engine electronic controlmodule 104 in this example is further configured to perform operationsto transmit, using the communication module, the static data, the repairdata, and the dynamic data to the external system 128.

Operations performed by the engine electronic control module 104 tostore dynamic data may include operations to retrieve dynamic data foreach engine component from the database, operations to update thedynamic data for each engine component after an engine cycle, operationsto transmit the updated dynamic data regarding its associated enginecomponent to each RFID tag for storage by the RFID tag, and operationsto test that each RFID tag stored the updated dynamic data for itsassociated engine component. Operations performed by the engineelectronic control module 104 to test that each RFID tag stored theupdated dynamic data for its associated engine component may includeoperations to retrieve the stored dynamic data from each RFID tag andoperations to compare the retrieved dynamic data with the updateddynamic data.

FIG. 2 is a process flow chart depicting an example process 200 in anaircraft-mounted controller for tracking engine component life cycledata. The example process 200 includes operations to receive static andrepair data from each RFID tag regarding the engine component with whichit is associated (operation 202). The static data may includeidentification information regarding the associated engine componentsuch as a part number and a serial number. The repair data may includerepair history information regarding the associated engine componentthat is recorded by the RFID tag, for example, during visits by theengine component to a repair shop.

The example process 200 includes operations to update an enginecomponents database with changes to each engine component's static andrepair data (operation 204). After receiving static and repair data fromone or more RFID tags, the database may be updated with any observedchanges. Alternatively, the entry for an engine component may be overwritten with received static and/or repair data from one or more RFIDtags regardless of whether the received data has any changes.

The example process 200 includes operations to compute dynamic data foreach engine component (operation 206). The dynamic data may includeengine usage information, component usage information, and componentfault information regarding the engine component. The engine usageinformation may include operating hours and operating cycles experiencedby the engine. The component usage information may include operatinghours and operating cycles experienced by the engine component. Thecomponent fault information may include fault codes and fault messages.The dynamic data may include environmental measurements such astemperature, vibration, ice accumulation, and others. The dynamic datafor one engine component may be different from the dynamic data foranother engine component. The computation of dynamic data may take placeduring each engine cycle, after each engine cycle or prior to thebeginning of the next engine cycle.

The example process 200 includes operations to update the enginecomponents database with changes to each engine component's dynamic data(operation 208). After computing dynamic data for one or more enginecomponents, the engine components database may be updated with anyobserved changes. Alternatively, the entry for an engine component maybe over written with newly computed dynamic data for one or more enginecomponents regardless of whether the computed data has changed. Thedynamic data updating may take place during each engine cycle, aftereach engine cycle or prior to the beginning of the next engine cycle.

The example process 200 also includes operations to send to each RFIDtag for storage the updated dynamic data for the engine component withwhich it is associated (operation 210). The dynamic data may be sent toone or more RFID tags prior to, in parallel with, or after the enginecomponents database is updated. The dynamic data may be sent to one ormore RFID tags during each engine cycle, after each engine cycle orprior to the beginning of the next engine cycle.

FIG. 3 is a process flow chart depicting another example process 300 inan aircraft-mounted controller for tracking engine component life cycledata. The example process 300 includes operations to retrieve from acomponent database static data, repair data, and dynamic data regardinga plurality of engine components (operation 302). The static dataincludes identification information regarding the engine component suchas a part number and a serial number. The repair data may include repairhistory information regarding the associated engine component that isrecorded by the RFID tag, for example, during visits by the enginecomponent to a repair shop. The dynamic data may include engine usageinformation, component usage information, and component faultinformation regarding the engine component. The engine usage informationmay include operating hours and operating cycles experienced by theengine. The component usage information may include operating hours andoperating cycles experienced by the engine component. The componentfault information may include fault codes and fault messages. Thedynamic data may include environmental measurements such as temperature,vibration, ice accumulation, and others. The dynamic data for one enginecomponent may be different from the dynamic data for another enginecomponent.

The example process 300 includes operations to transmit, using thecommunication module, the dynamic data regarding the associated enginecomponent to each RFID tag for storage in the RFID tag (operation 304).The dynamic data may be sent to one or more RFID tags during an enginecycle, after an engine cycle or prior to the beginning of an enginecycle.

The example process 300 includes operations to transmit, using thecommunication module, static data, repair data, and dynamic dataregarding one of the engine components to an external system responsiveto a request by the external system (operation 306). The static data,repair data, and dynamic data may be sent for one, a plurality of or allRFID tags responsive to a request. The static data, repair data, anddynamic data may be sent prior to, in parallel with, or after thedynamic data is sent to one or more RFID tags. The static data, repairdata, and dynamic data may be sent during an engine cycle, after anengine cycle or prior to the beginning of an engine cycle.

FIG. 4 is a process flow chart depicting another example process 400 inan aircraft-mounted controller for tracking engine component life cycledata. The example process 400 includes operations to retrieve from acomponent database static data, repair data, and dynamic data regardingthe plurality of engine components (operation 402). The static dataincludes identification information regarding the engine component suchas a part number and a serial number. The repair data may include repairhistory information regarding the associated engine component that isrecorded by the RFID tag, for example, during visits by the enginecomponent to a repair shop. The dynamic data may include engine usageinformation, component usage information, and component faultinformation regarding the engine component. The engine usage informationmay include operating hours and operating cycles experienced by theengine. The component usage information may include operating hours andoperating cycles experienced by the engine component. The componentfault information may include fault codes and fault messages. Thedynamic data may include environmental measurements such as temperature,vibration, ice accumulation, and others. The dynamic data for one enginecomponent may be different from the dynamic data for another enginecomponent.

The example process 400 includes operations to transmit, using thecommunication module, the dynamic data regarding the associated enginecomponent to each RFID tag for storage in the RFID tag (operation 404).The dynamic data may be sent to one or more RFID tags during an enginecycle, after an engine cycle or prior to the beginning of an enginecycle.

The example process 400 includes operations to transmit, using thecommunication module, static data, repair data, and dynamic dataregarding one of the engine components to an external system responsiveto a request by the external system (operation 406). The static data,repair data, and dynamic data may be sent for one, a plurality of or allRFID tags responsive to a request. The static data, repair data, anddynamic data may be sent prior to, in parallel with, or after thedynamic data is sent to one or more RFID tags. The static data, repairdata, and dynamic data may be sent during an engine cycle, after anengine cycle or prior to the beginning of an engine cycle.

The example process 400 includes operations to analyze the dynamic dataregarding at least one engine component (operation 408). After theanalysis, the example process 400 includes operations to transmit, usingthe communication module, a notification regarding at least one enginecomponent to a system external to the aircraft responsive to a conditionobserved or calculated from the dynamic data (operation 410). After theanalysis, the example process 400 includes operations to transmit, usingthe communication module, static data, repair data, and dynamic dataregarding the at least one engine component to a system external to theaircraft responsive to a condition observed from the dynamic data(operation 412). After the analysis, the example process 400 alsoincludes operations to transmit, using the communication module, staticdata, repair data, and dynamic data regarding the at least one enginecomponent to a system external to the aircraft responsive to a conditioncalculated from the dynamic data (operation 414). The notification,static data, repair data, and/or dynamic data may be sent during anengine cycle, after an engine cycle or prior to the beginning of anengine cycle.

FIG. 5 is a process flow chart depicting another example process 500 inan aircraft-mounted controller for tracking engine component life cycledata. The example process 500 includes operations to request that eachRFID tag provide static and repair data regarding the engine componentwith which it is associated (operation 502). The static data may includeidentification information regarding the associated engine componentsuch as a part number and a serial number. The repair data may includerepair history information regarding the associated engine componentthat is recorded by the RFID tag, for example, during visits by theengine component to a repair shop.

The example process 500 includes operations to update an enginecomponents database with changes to each engine component's static andrepair data (operation 504). After receiving static and repair data fromone or more RFID tags, the database may be updated with any observedchanges. Alternatively, the entry for an engine component may be overwritten with received static and/or repair data from one or more RFIDtags regardless of whether the received data has any changes.

The example process 500 includes operations to compute dynamic data foreach engine component (operation 506). The dynamic data may includeengine usage information, component usage information, and componentfault information regarding the engine component. The engine usageinformation may include operating hours and operating cycles experiencedby the engine. The component usage information may include operatinghours and operating cycles experienced by the engine component. Thecomponent fault information may include fault codes and fault messages.The dynamic data may include environmental measurements such astemperature, vibration, ice accumulation, and others. The dynamic datafor one engine component may be different from the dynamic data foranother engine component. The computation of dynamic data may take placeduring each engine cycle, after each engine cycle or prior to thebeginning of the next engine cycle.

The example process 500 includes operations to update the enginecomponents database with changes to each engine component's dynamic data(operation 508). After computing dynamic data for one or more enginecomponents, the engine components database may be updated with anyobserved changes. Alternatively, the entry for an engine component maybe over written with newly computed dynamic data for one or more enginecomponents regardless of whether the computed data has changed. Thedynamic data updating may take place during each engine cycle, aftereach engine cycle or prior to the beginning of the next engine cycle.

The example process 500 also includes operations to send to each RFIDtag for storage the updated dynamic data for the engine component withwhich it is associated (operation 510). The dynamic data may be sent toone or more RFID tags prior to, in parallel with, or after the enginecomponents database is updated. The dynamic data may be sent to one ormore RFID tags during each engine cycle, after each engine cycle orprior to the beginning of the next engine cycle.

The example process 500 includes operations to transmit, using thecommunication module, static data, repair data, and dynamic dataregarding one of the engine components to an external system responsiveto a request by the external system (operation 512). The static data,repair data, and dynamic data may be sent for one, a plurality of, orall RFID tags responsive to a request. The static data, repair data, anddynamic data may be sent prior to, in parallel with, or after thedynamic data is sent to one or more RFID tags. The static data, repairdata, and dynamic data may be sent during an engine cycle, after anengine cycle or prior to the beginning of an engine cycle.

The example process 500 includes operations to analyze the dynamic dataregarding at least one engine component (operation 514). After theanalysis, the example process 500 includes operations to transmit, usingthe communication module, a notification regarding at least one enginecomponent to a system external to the aircraft responsive to a conditionobserved or calculated from the dynamic data (operation 516). After theanalysis, the example process 500 includes operations to transmit, usingthe communication module, static data, repair data, and dynamic dataregarding the at least one engine component to a system external to theaircraft responsive to a condition observed from the dynamic data(operation 518). After the analysis, the example process 500 alsoincludes operations to transmit, using the communication module, staticdata, repair data, and dynamic data regarding the at least one enginecomponent to a system external to the aircraft responsive to a conditioncalculated from the dynamic data (operation 520). The notification,static data, repair data, and/or dynamic data may be sent during anengine cycle, after an engine cycle or prior to the beginning of anengine cycle.

Described herein are techniques for tracking engine component life cycledata. RFID tags positioned around the engine on or near LRUs and otherengine components can record identification information regarding theassociated engine component such as a part number and a serial number,repair data such as repair history information regarding the associatedengine component, and dynamic data such as engine usage information,component usage information, component fault information, andenvironmental measurements such as temperature, vibration, iceaccumulation, and others regarding the engine component. A controllercan record the identification information, the repair data, and dynamicdata for each engine component in a database and transmit specificengine component dynamic data to the RFID tags for storage. Thecontroller can be configured to analyze the data and providenotifications regarding component conditions. The system allows for abill of material of engine components to be automatically recorded andcombined with actual component operation hours and cycle data. This canprovide an automated tracking system for tracking LRU life in hours orMean Time Between Removals or Overhaul. The automatic writing of thedynamic information directly to the RFID tag may allow improved trackingof component hours for maintenance and reliability data tracking. Thesystem may allow for improved engine health monitoring algorithms andcomponent reliability data tracking.

In one embodiment, an engine-mounted component life cycle data trackingsystem is provided. The system comprises a plurality of radio frequencyidentification (RFID) tags positioned around an aircraft engine whereineach RFID tag is associated with and positioned proximate to a differentengine component and each RFID tag configured to transmit and store dataregarding its associated engine component. The system further comprisesan engine-mounted communication module configured to read data from andwrite data to each RFID tag and an aircraft-mounted controller incommunication with the engine-mounted communication module. Theaircraft-mounted controller is configured to perform operations toretrieve, using the communication module, static data and repair datafrom each RFID tag wherein the static data includes identificationinformation regarding the engine components and the repair data includesrepair history information regarding the engine components resultingfrom any visit by any of the engine components to any repair shop. Theaircraft-mounted controller is further configured to store the staticdata and the repair data for each engine component in a database in thecontroller and store dynamic data in the database for each enginecomponent after each engine cycle wherein the dynamic data comprisesengine usage information, component usage information, and componentfault information regarding the engine component. The aircraft-mountedcontroller is further configured to transmit, using the communicationmodule, the dynamic data regarding the engine component to each RFID tagafter each engine cycle for storage in the RFID tag.

These aspects and other embodiments may include one or more of thefollowing features. The operations to store dynamic data may compriseoperations to retrieve dynamic data for each engine component from thedatabase, update the dynamic data for each engine component after anengine cycle, transmit the updated dynamic data regarding the associatedengine component to each RFID tag for storage, and test that each RFIDtag stored the updated dynamic data for its associated engine component.The operations to test may comprise operations to retrieve the storeddynamic data from each RFID tag and compare the retrieved dynamic datawith the updated dynamic data. The communication module may be furtherconfigured to communicate wirelessly with an external system. Thecontroller may be further configured to perform operations to transmit,using the communication module, the static data, the repair data, andthe dynamic data to the external system. The engine usage informationmay comprise operating hours and operating cycles experienced by theengine, the component usage information may comprise operating hours andoperating cycles experienced by the engine component, and the componentfault information may comprise fault codes and fault messages. Theengine components may comprise a plurality of line replaceable units(LRUs) and a plurality of components other than LRUs.

In another embodiment, an engine component data tracking system isprovided. The system comprises an engine-mounted communication moduleconfigured to read data from and write data to a plurality of radiofrequency identification (RFID) tags positioned around an aircraftengine wherein each RFID tag is associated with and positioned proximateto a different one of a plurality of engine components and each RFID tagis configured to transmit and store data regarding its associated enginecomponent. The system further comprises an aircraft-mounted controllerin communication with the engine-mounted communication module. Theaircraft-mounted controller is configured to perform operations toretrieve from a component database static data, repair data, and dynamicdata regarding the plurality of engine components wherein the staticdata includes identification information regarding the engine component,the repair data includes repair history information regarding the enginecomponent resulting from any visit by the engine component to any repairshop, and the dynamic data comprises engine usage information, componentusage information, and component fault information regarding the enginecomponent. The aircraft-mounted controller is further configured toperform operations to transmit, using the communication module, thedynamic data regarding the engine component to each RFID tag after eachengine cycle for storage in the RFID tag and transmit, using thecommunication module, static data, repair data, and dynamic dataregarding one of the engine components to an external system responsiveto a request by the external system.

These aspects and other embodiments may include one or more of thefollowing features. The aircraft-mounted controller may be furtherconfigured to perform operations to analyze the dynamic data regardingat least one engine component. The aircraft-mounted controller may befurther configured to transmit, using the communication module, anotification regarding the at least one engine component to a systemexternal to the aircraft responsive to a condition observed orcalculated from the dynamic data. The aircraft-mounted controller may befurther configured to transmit, using the communication module, staticdata, repair data, and dynamic data regarding the at least one enginecomponent to a system external to the aircraft responsive to a conditionobserved or calculated from the dynamic data. The communication modulemay be further configured to communicate wirelessly with the externalsystem. The engine usage information may comprise operating hours andoperating cycles experienced by the engine, the component usageinformation may comprise operating hours and operating cyclesexperienced by the engine component, and the component fault informationmay comprise fault codes and fault messages. The engine components maycomprise a plurality of line replaceable units (LRUs) and a plurality ofcomponents other than LRUs. The controller may be engine mounted.

In another embodiment, an aircraft-mounted controller is provided. Thecontroller comprises one or more processors and non-transient computerreadable media encoded with programming instructions that cause the oneor more processors to implement a method. The implemented methodcomprises reading data from and writing data to a plurality of radiofrequency identification (RFID) tags positioned around an aircraftengine wherein each RFID tag is associated with and positioned proximateto a different one of a plurality of engine components and each RFID tagis configured to transmit and store data regarding its associated enginecomponent. The method further comprises storing in a component databasestatic data, repair data, and dynamic data regarding the plurality ofengine components wherein the static data includes identificationinformation regarding the engine component, the repair data includesrepair history information regarding the engine component that isrecorded by the RFID tag during visits by the engine component to arepair shop, and the dynamic data comprises engine usage information,component usage information, and component fault information regardingthe engine component. The method further comprises transmitting thedynamic data regarding the engine component to each RFID tag after eachengine cycle for storage in the RFID tag and transmitting static data,repair data, and dynamic data regarding one of the engine components toan external system responsive to a request by the external system.

These aspects and other embodiments may include one or more of thefollowing features. The controller may be further configured to performoperations to analyze the dynamic data regarding at least one enginecomponent. The controller may be further configured to transmit anotification regarding the at least one engine component to a systemexternal to the aircraft responsive to a condition observed orcalculated from the dynamic data. The controller may be furtherconfigured to transmit static data, repair data, and dynamic dataregarding the at least one engine component to a system external to theaircraft responsive to a condition observed or calculated from thedynamic data. The engine usage information may comprise operating hoursand operating cycles experienced by the engine, the component usageinformation may comprise operating hours and operating cyclesexperienced by the engine component, and the component fault informationmay comprise fault codes and fault messages. The engine components maycomprise a plurality of line replaceable units (LRUs) and a plurality ofcomponents other than LRUs. The controller may be engine mounted. Thecontroller may comprise an engine mounted communications module.

In another embodiment, an engine mounted communications module isprovided. The engine mounted communications module comprises one or moreprocessors and non-transient computer readable media encoded withprogramming instructions that cause the one or more processors toimplement a method. The implemented method comprises reading data fromand writing data to a plurality of radio frequency identification (RFID)tags positioned around an aircraft engine wherein each RFID tag isassociated with and positioned proximate to a different one of aplurality of engine components and each RFID tag is configured totransmit and store data regarding its associated engine component. Themethod further comprises storing in a component database static data,repair data, and dynamic data regarding the plurality of enginecomponents wherein the static data includes identification informationregarding the engine component, the repair data includes repair historyinformation regarding the engine component that is recorded by the RFIDtag during visits by the engine component to a repair shop, and thedynamic data comprises engine usage information, component usageinformation, and component fault information regarding the enginecomponent. The method further comprises transmitting the dynamic dataregarding the engine component to each RFID tag after each engine cyclefor storage in the RFID tag and transmitting static data, repair data,and dynamic data regarding one of the engine components to an externalsystem responsive to a request by the external system.

These aspects and other embodiments may include one or more of thefollowing features. The engine mounted communications module may befurther configured to perform operations to analyze the dynamic dataregarding at least one engine component. The engine mountedcommunications module may be further configured to transmit anotification regarding the at least one engine component to a systemexternal to the aircraft responsive to a condition observed orcalculated from the dynamic data. The engine mounted communicationsmodule may be further configured to transmit static data, repair data,and dynamic data regarding the at least one engine component to a systemexternal to the aircraft responsive to a condition observed orcalculated from the dynamic data. The engine usage information maycomprise operating hours and operating cycles experienced by the engine,the component usage information may comprise operating hours andoperating cycles experienced by the engine component, and the componentfault information may comprise fault codes and fault messages. Theengine components may comprise a plurality of line replaceable units(LRUs) and a plurality of components other than LRUs.

Those of skill in the art will appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the embodiments disclosed herein may be implemented aselectronic hardware, computer software, or combinations of both. Some ofthe embodiments and implementations are described above in terms offunctional and/or logical block components (or modules) and variousprocessing steps. However, it should be appreciated that such blockcomponents (or modules) may be realized by any number of hardware,software, and/or firmware components configured to perform the specifiedfunctions. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the present invention. For example, anembodiment of a system or a component may employ various integratedcircuit components, e.g., memory elements, digital signal processingelements, logic elements, look-up tables, or the like, which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices. In addition, those skilled inthe art will appreciate that embodiments described herein are merelyexemplary implementations.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general-purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with theembodiments disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal

In this document, relational terms such as first and second, and thelike may be used solely to distinguish one entity or action from anotherentity or action without necessarily requiring or implying any actualsuch relationship or order between such entities or actions. Numericalordinals such as “first,” “second,” “third,” etc. simply denotedifferent singles of a plurality and do not imply any order or sequenceunless specifically defined by the claim language. The sequence of thetext in any of the claims does not imply that process steps must beperformed in a temporal or logical order according to such sequenceunless it is specifically defined by the language of the claim. Theprocess steps may be interchanged in any order without departing fromthe scope of the invention if such an interchange does not contradictthe claim language and is not logically nonsensical.

Furthermore, depending on the context, words such as “connect” or“coupled to” used in describing a relationship between differentelements do not imply that a direct physical connection must be madebetween these elements. For example, two elements may be connected toeach other physically, electronically, logically, or in any othermanner, through one or more additional elements.

While at least one exemplary embodiment has been presented in theforegoing detailed description of the invention, it should beappreciated that a vast number of variations exist. As an example, inother embodiments the example processes 200, 300, 400, and 500 may beperformed by an engine-mounted communication module. It should also beappreciated that the exemplary embodiment or exemplary embodiments areonly examples, and are not intended to limit the scope, applicability,or configuration of the invention in any way. Rather, the foregoingdetailed description will provide those skilled in the art with aconvenient road map for implementing an exemplary embodiment of theinvention. It being understood that various changes may be made in thefunction and arrangement of elements described in an exemplaryembodiment without departing from the scope of the invention as setforth in the appended claims.

What is claimed is:
 1. An engine-mounted component life cycle datatracking system, comprising: a plurality of radio frequencyidentification (RFID) tags associated with, positioned proximate to, andconfigured to transmit and store identification, repair history, anddynamic data regarding a different engine component of a plurality ofengine components, the dynamic data comprising engine usage, componentusage, and/or component fault information; and an aircraft-mountedcontroller including non-transient computer readable storage media, thecontroller configured to: store identification and repair history dataretrieved from the RFID tags in the storage media; store dynamic datafor the plurality of engine components in the storage media after eachengine cycle; and transmit dynamic data to the RFID tags after eachengine cycle for storage; wherein after each engine cycle theaircraft-mounted controller includes in its non-transient computerreadable storage media a database of the identification, repair historyand dynamic data for the plurality of engine component, and the RFIDtags include the identification, repair history and dynamic data for itsassociated engine component.
 2. The system of claim 1 wherein to storedynamic data the controller is configured to: retrieve dynamic data foreach engine component from the storage media in the aircraft-mountedcontroller; update the dynamic data for each engine component after anengine cycle; transmit the updated dynamic data regarding the associatedengine component to each RFID tag for storage; and test that each RFIDtag stored the updated dynamic data for its associated engine component.3. The system of claim 2 wherein to test the controller is configured toretrieve the stored dynamic data from each RFID tag and compare theretrieved dynamic data with the updated dynamic data.
 4. The system ofclaim 1 wherein the controller is further configured to communicatewirelessly with an external system.
 5. The system of claim 4 wherein thecontroller is further configured to transmit the static data, the repairdata, and the dynamic data to the external system.
 6. The system ofclaim 1 wherein: the engine usage information comprises operating hoursand operating cycles experienced by the engine, the component usageinformation comprises operating hours and operating cycles experiencedby the engine component, and the component fault information comprisesfault codes and fault messages.
 7. The system of claim 1 wherein theengine components comprise a plurality of line replaceable units (LRUs)and a plurality of components other than LRUs.
 8. An aircraft-mountedcontroller for tracking engine component data, the controller includingnon-transient computer readable storage media configured to storeidentification, repair history, and dynamic data for a plurality ofaircraft engine components having an associated radio frequencyidentification (RFID) tag that is configured to transmit and storeidentification, repair history, and dynamic data regarding itsassociated engine component, the dynamic data comprising engine usage,component usage, and/or component fault information, the controllerconfigured to: store identification and repair history data retrievedfrom the RFID tags in the storage media; store dynamic data for theplurality of engine components in the storage media after each enginecycle; and transmit dynamic data to the RFID tags after each enginecycle for storage; wherein after each engine cycle the aircraft-mountedcontroller includes in its non-transient computer readable storage mediaa database of the identification, repair history and dynamic data forthe plurality of engine components.
 9. The aircraft-mounted controllerof claim 8, further configured to analyze the dynamic data regarding atleast one engine component.
 10. The aircraft-mounted controller of claim9, further configured to transmit a notification regarding the at leastone engine component to a system external to the aircraft responsive toa condition observed or calculated from the dynamic data.
 11. Theaircraft-mounted controller of claim 9, further configured to transmitstatic data, repair data, and dynamic data regarding the at least oneengine component to a system external to the aircraft responsive to acondition observed or calculated from the dynamic data.
 12. Theaircraft-mounted controller of claim 8, further configured tocommunicate wirelessly with the external system.
 13. Theaircraft-mounted controller of claim 8 wherein: the engine usageinformation comprises operating hours and operating cycles experiencedby the engine, the component usage information comprises operating hoursand operating cycles experienced by the engine component, and thecomponent fault information comprises fault codes and fault messages.14. The aircraft-mounted controller of claim 8, wherein the controlleris engine mounted.
 15. Non-transient computer readable storage media:configured to store identification, repair history, and dynamic data fora plurality of aircraft engine components having an associated radiofrequency identification (RFID) tag that is configured to transmit andstore identification, repair history, and dynamic data regarding itsassociated engine component, the dynamic data comprising engine usage,component usage, and/or component fault information; and encoded withprogramming instructions configurable to cause a processor in acontroller on an aircraft to perform a method, the method comprising:storing identification and repair history data retrieved from the RFIDtags in the storage media; storing dynamic data for the plurality ofengine components in the storage media after each engine cycle; andtransmitting dynamic data to the RFID tags after each engine cycle forstorage; wherein after each engine cycle the non-transient computerreadable storage media includes a database of the identification, repairhistory and dynamic data for the plurality of engine components.
 16. Thenon-transient computer readable media of claim 15, wherein storingdynamic data comprises: retrieving dynamic data for each enginecomponent from the storage media; updating the dynamic data for eachengine component after an engine cycle; transmitting the updated dynamicdata regarding the associated engine component to each RFID tag forstorage; and testing that each RFID tag stored the updated dynamic datafor its associated engine component.
 17. The non-transient computerreadable media of claim 16 wherein testing comprises retrieving thestored dynamic data from each RFID tag and comparing the retrieveddynamic data with the updated dynamic data.
 18. The non-transientcomputer readable media of claim 15, wherein the method furthercomprises transmitting the static data, the repair data, and the dynamicdata to a system external to the aircraft responsive to a conditionobserved or calculated from the dynamic data.
 19. The non-transientcomputer readable media of claim 15, wherein: the engine usageinformation comprises operating hours and operating cycles experiencedby the engine, the component usage information comprises operating hoursand operating cycles experienced by the engine component, and thecomponent fault information comprises fault codes and fault messages.20. The non-transient computer readable media of claim 15, wherein themethod further comprises transmitting a notification regarding at leastone engine component to a system external to the aircraft responsive toa condition observed or calculated from the dynamic data.